You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure what in the bot procedure is causing this to time out consistently, but i was not able to replicate it manually neither with EESSI-extend only or eessi_container + EESSI_extend.
Since all other tests are always passing i think it is safe to ignore the tests for OpenBabel on a64fx
We could even change pretestopts to echo "Skipping tests" || to not run them at all...
New job on instance eessi-bot-mc-aws for repository eessi.io-2023.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2026.02/pr_160/129661
date
job status
comment
Feb 10 20:08:46 UTC 2026
submitted
job id 129661 awaits release by job manager
Feb 10 20:09:35 UTC 2026
released
job awaits launch by Slurm scheduler
Feb 10 20:15:41 UTC 2026
running
job 129661 is running
Feb 10 20:19:50 UTC 2026
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-129661.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.* created!
Artefacts
eessi-2023.06-software-linux-x86_64-amd-zen2-17707545500.tar.zstsize: 0 MiB (26178 bytes) entries: 1 modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all
no module files in tarball
software under 2023.06/software/linux/x86_64/amd/zen2/software
no software packages in tarball
reprod directories under 2023.06/software/linux/x86_64/amd/zen2/reprod
no reprod directories in tarball
other under 2023.06/software/linux/x86_64/amd/zen2
New job on instance eessi-bot-mc-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2026.02/pr_160/129662
date
job status
comment
Feb 10 20:08:51 UTC 2026
submitted
job id 129662 awaits release by job manager
Feb 10 20:09:32 UTC 2026
released
job awaits launch by Slurm scheduler
Feb 10 20:15:37 UTC 2026
running
job 129662 is running
Feb 10 20:17:46 UTC 2026
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-129662.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.* created!
Artefacts
eessi-2025.06-software-linux-x86_64-amd-zen2-17707545400.tar.zstsize: 0 MiB (26184 bytes) entries: 1 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all
no module files in tarball
software under 2025.06/software/linux/x86_64/amd/zen2/software
no software packages in tarball
reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod
no reprod directories in tarball
other under 2025.06/software/linux/x86_64/amd/zen2
2025.06/init/easybuild/eb_hooks.py
Feb 10 20:17:46 UTC 2026
test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ OK ] (1/4) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.5-gompi-2025a %scale=1_node %device_type=cpu /e4bf9965 @BotBuildTests:x86-64-zen2+default P: latency: 1.3 us (r:0, l:None, u:None) [ OK ] (2/4) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.5-gompi-2025a %scale=1_node %device_type=cpu /3da4890b @BotBuildTests:x86-64-zen2+default P: latency: 2.02 us (r:0, l:None, u:None) [ OK ] (3/4) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.5-gompi-2025a %scale=1_node /3255009a @BotBuildTests:x86-64-zen2+default P: latency: 0.18 us (r:0, l:None, u:None) [ OK ] (4/4) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.5-gompi-2025a %scale=1_node /59f4b331 @BotBuildTests:x86-64-zen2+default P: bandwidth: 7860.57 MB/s (r:0, l:None, u:None) [ PASSED ] Ran 4/4 test case(s) from 4 check(s) (0 failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-129662.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Feb 10 20:26:39 UTC 2026
uploaded
transfer of eessi-2025.06-software-linux-x86_64-amd-zen2-17707545400.tar.zst to S3 bucket succeeded
I am not sure what in the bot procedure is causing this to time out consistently, but i was not able to replicate it manually neither with EESSI-extend only or eessi_container + EESSI_extend.
Since all other tests are always passing i think it is safe to ignore the tests for OpenBabel on a64fx We could even change pretestopts to echo "Skipping tests" || to not run them at all...
@Crivella Running the tests is always better, since then we have the test result in the installation log...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See EESSI/software-layer#1332 (comment)
I am not sure what in the bot procedure is causing this to time out consistently, but i was not able to replicate it manually neither with
EESSI-extendonly oreessi_container+EESSI_extend.Since all other tests are always passing i think it is safe to ignore the tests for OpenBabel on
a64fxWe could even change
pretestoptstoecho "Skipping tests" ||to not run them at all...